Fix pdfjs-dist/webpack causing errors with certain configs #11964
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using
require.resolve("worker-loader")
to check ifworker-loader
is installed causes webpack to includeworker-loader
in the output bundle (see docs), which is not the intended effect. Aside from increasing the bundle size unnecessarily, it also causes errors for webpack configs with targets that don't have node's built-in modules.These errors can be fixed by configuring webpack
externals
to excludeworker-loader
, but it's more difficult to figure out this solution than to figure out thatworker-loader
needs to be installed (even without this explicit error message).To solve this, the explicit check for
worker-loader
has been removed. An alternative solution would be to use webpack's resolveWeak. Documentation has also been added inexamples/webpack
to help users.The check was originally added in PR #11474. I've set up a minimal project to demonstrate the issue here.